Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes: #264
Fixes: #230
After extensive research and several attempts, it's evident that the reported issue isn't a bug but rather a result of using devon instead of ideasy while installing new tools. For instance:
The problem we were getting was that the moving of the installed software directory fails because of the windows file lock on the directory, e.g.
java.lang.IllegalStateException: Failed to move D:\projects\IDEasy\software\java to D:\projects\IDEasy\updates\backups\2024-03-22\java_17-13-29
.This issue specifically arises when the tools are installed using 'devon' (as a directory) instead of 'ideasy' (as a junction).
When installed with 'ideasy', the file lock automatically applies to the target path of the junction
IDE_ROOT/_ide/software/default/...
, allowing the deletion of the junction itself inIDE_HOME/software/
. Consequently, updating a tool version becomes seamless.The only fix it had to be implemented is for a another exception that was arising in the
delete
method inFileaccessImpl
, that wasn't properly recognizing and deleting junctions.